Handling Of Invalid Mandatory Information In Mobile Communications

ABSTRACT

Various examples and schemes pertaining to handling of invalid mandatory information in mobile communications are described. An apparatus (e.g., a user equipment (UE)) receives a 5th Generation session management (5GSM) message from a network node of a wireless network. The apparatus determines that there is an error encountered with a mandatory information element (IE) in the 5GSM message. The apparatus handles the error in a way specific to a protocol data unit (PDU) session procedure corresponding to the 5GSM message.

CROSS REFERENCE TO RELATED PATENT APPLICATION(S)

The present disclosure is part of a non-provisional application claimingthe priority benefit of U.S. Patent Application No. 62/742,325, filed on6 Oct. 2018, the content of which being incorporated by reference in itsentirety.

TECHNICAL FIELD

The present disclosure is generally related to mobile communicationsand, more particularly, to handling of invalid mandatory information inmobile communications.

BACKGROUND

Unless otherwise indicated herein, approaches described in this sectionare not prior art to the claims listed below and are not admitted asprior art by inclusion in this section.

Under the 3^(rd) Generation Partnership Project (3GPP) specifications,non-access stratum (NAS) procedures in a 5th Generation system (5GS) canbe used for 5GS mobility management between a user equipment (UE) and anAccess and Mobility Management Function (AMF) for both 3GPP access andnon-3GPP access. The NAS procedures can also be used for 5GS sessionmanagement between the UE and a Session Management Function (SMF) forboth 3GPP access and non-3GPP access. Specifically, the 5G SessionManagement (5GSM) protocol defined in the 3GPP specifications (e.g., TS24.301) provides procedures for the handling of 5GS protocol data unit(PDU) session contexts. Together with the bearer control provided by theaccess stratum (AS), the 5GSM protocol is used for the control of userplane (UP) bearers, as the 5G Session Management Function (SMF) isresponsible for interacting with the decoupled data plane, creating,updating and removing PDU sessions and managing session context with theUser Plane Function (UPF). Currently, however, it has not been definedas to how errors in non-semantical mandatory information elements shouldbe handled for certain PDU session related procedures.

SUMMARY

The following summary is illustrative only and is not intended to belimiting in any way. That is, the following summary is provided tointroduce concepts, highlights, benefits and advantages of the novel andnon-obvious techniques described herein. Select implementations arefurther described below in the detailed description. Thus, the followingsummary is not intended to identify essential features of the claimedsubject matter, nor is it intended for use in determining the scope ofthe claimed subject matter.

In one aspect, a method may involve a processor of an apparatusreceiving a 5GSM message from a network node of a wireless network. Themethod may also involve the processor determining that there is an errorencountered with a mandatory information element (IE) in the 5GSMmessage. The method may further involve the processor handing the errorin a way specific to a PDU session procedure corresponding to the 5GSMmessage.

In one aspect, a method may involve a processor of an apparatusdetermining that there is an error encountered with a mandatory IE in a5GSM message from a network node of a wireless network. The method mayalso involve the processor handling the error in a way depending on towhich PDU session procedure the 5GSM message corresponds. The PDUsession procedure to which the 5GSM message corresponds may be a PDUsession establishment procedure, a PDU session modification procedure,or a PDU session release procedure.

In one aspect, an apparatus may include a transceiver and a processorcoupled to the transceiver. The transceiver may be configured towirelessly communicate with a network node of a wireless network. Theprocessor may be configured to receive, via the transceiver, a 5GSMmessage from the network node. The processor may be also configured todetermine that there is an error encountered with a mandatory IE in the5GSM message. The processor may be further configured to handle theerror in a way specific to a PDU session procedure corresponding to the5GSM message.

It is noteworthy that, although description provided herein may be inthe context of certain radio access technologies, networks and networktopologies such as 5G and New Radio (NR), the proposed concepts, schemesand any variation(s)/derivative(s) thereof may be implemented in, forand by other types of radio access technologies, networks and networktopologies such as, for example and without limitation, Long-TermEvolution (LTE), LTE-Advanced, LTE-Advanced Pro, narrowband (NB),narrowband Internet of Things (NB-IoT), and any future-developednetworks and technologies. Thus, the scope of the present disclosure isnot limited to the examples described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a furtherunderstanding of the disclosure and are incorporated in and constitute apart of the present disclosure. The drawings illustrate implementationsof the disclosure and, together with the description, serve to explainthe principles of the disclosure. It is appreciable that the drawingsare not necessarily in scale as some components may be shown to be outof proportion than the size in actual implementation in order to clearlyillustrate the concept of the present disclosure.

FIG. 1 is a diagram of an example network environment in which variousproposed schemes in accordance with the present disclosure may beimplemented.

FIG. 2 is a block diagram of an example communication system inaccordance with an implementation of the present disclosure.

FIG. 3 is a flowchart of an example process in accordance with animplementation of the present disclosure.

FIG. 4 is a flowchart of an example process in accordance with animplementation of the present disclosure.

DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

Detailed embodiments and implementations of the claimed subject mattersare disclosed herein. However, it shall be understood that the disclosedembodiments and implementations are merely illustrative of the claimedsubject matters which may be embodied in various forms. The presentdisclosure may, however, be embodied in many different forms and shouldnot be construed as limited to the exemplary embodiments andimplementations set forth herein. Rather, these exemplary embodimentsand implementations are provided so that description of the presentdisclosure is thorough and complete and will fully convey the scope ofthe present disclosure to those skilled in the art. In the descriptionbelow, details of well-known features and techniques may be omitted toavoid unnecessarily obscuring the presented embodiments andimplementations.

OVERVIEW

Implementations in accordance with the present disclosure relate tovarious techniques, methods, schemes and/or solutions pertaining tohandling of invalid mandatory information in mobile communications.According to the present disclosure, a number of possible solutions maybe implemented separately or jointly. That is, although these possiblesolutions may be described below separately, two or more of thesepossible solutions may be implemented in one combination or another.

FIG. 1 illustrates an example network environment 100 in which varioussolutions and schemes in accordance with the present disclosure may beimplemented. Referring to FIG. 1, network environment 100 may involve aUE 110 in wireless communication with a wireless network 120 (e.g., a 5GNR mobile network or an NB-IoT network) via a network node 125 (e.g., abase station such as an eNB, a gNB or a transmit-receive point (TRP)).In network environment 100, UE 110 and wireless network 120 mayimplement various schemes pertaining handling of invalid mandatoryinformation in mobile communications in accordance with the presentdisclosure.

Under various proposed schemes in accordance with the presentdisclosure, UE 110 may receive a 5GSM message for a PDU session-relatedprocedure from wireless network 120 via network node 125 and maydetermine that there is an error encountered with a mandatory IE in the5GSM message. Accordingly, UE 110 may handle the error in a way specificto the PDU session-related procedure, which may be a PDU sessionestablishment procedure, a PDU session modification procedure, or a PDUsession release procedure.

Under a proposed scheme in accordance with the present disclosure, in anevent that the 5GSM message corresponds to a PDU SESSION ESTABLISHMENTACCEPT message, UE 110 may handle the error by initiating a PDU sessionrelease procedure. For instance, UE 110 may send a PDU SESSION RELEASEREQUEST message to network node 125 with a 5GSM cause #96 to indicateinvalid mandatory information.

Under another proposed scheme in accordance with the present disclosure,in an event that the 5GSM message corresponds to a PDU SESSIONMODIFICATION COMMAND message, UE 110 may handle the error by sending aPDU SESSION MODIFICATION COMMAND REJECT message to network node 125 witha 5GSM cause #96 to indicate invalid mandatory information.

Under yet another proposed scheme in accordance with the presentdisclosure, in an event that the 5GSM message corresponds to a PDUSESSION RELEASE COMMAND message, UE 110 may handle the error by sendinga PDU SESSION RELEASE COMPLETE message to network node 125 with a 5GSMcause #96 to indicate invalid mandatory information.

ILLUSTRATIVE IMPLEMENTATIONS

FIG. 2 illustrates an example communication system 200 having an exampleapparatus 210 and an example apparatus 220 in accordance with animplementation of the present disclosure. Each of apparatus 210 andapparatus 220 may perform various functions to implement schemes,techniques, processes and methods described herein pertaining tohandling of invalid mandatory information in mobile communications,including various schemes described above as well as process 400described below.

Each of apparatus 210 and apparatus 220 may be a part of an electronicapparatus, which may be a UE such as a portable or mobile apparatus, awearable apparatus, a wireless communication apparatus or a computingapparatus. For instance, each of apparatus 210 and apparatus 220 may beimplemented in a smartphone, a smartwatch, a personal digital assistant,a digital camera, or a computing equipment such as a tablet computer, alaptop computer or a notebook computer. Each of apparatus 210 andapparatus 220 may also be a part of a machine type apparatus, which maybe an IoT or NB-IoT apparatus such as an immobile or a stationaryapparatus, a home apparatus, a wire communication apparatus or acomputing apparatus. For instance, each of apparatus 210 and apparatus220 may be implemented in a smart thermostat, a smart fridge, a smartdoor lock, a wireless speaker or a home control center. Alternatively,each of apparatus 210 and apparatus 220 may be implemented in the formof one or more integrated-circuit (IC) chips such as, for example andwithout limitation, one or more single-core processors, one or moremulti-core processors, one or more complex-instruction-set-computing(CISC) processors, or one or more reduced-instruction-set-computing(RISC) processors. Each of apparatus 210 and apparatus 220 may includeat least some of those components shown in FIG. 2 such as a processor212 and a processor 222, respectively. Each of apparatus 210 andapparatus 220 may further include one or more other components notpertinent to the proposed scheme of the present disclosure (e.g.,internal power supply, display device and/or user interface device),and, thus, such component(s) of each of apparatus 210 and apparatus 220are neither shown in FIG. 2 nor described below in the interest ofsimplicity and brevity.

In some implementations, at least one of apparatus 210 and apparatus 220may be a part of an electronic apparatus, which may be a network node orbase station (e.g., eNB, gNB or TRP), a small cell, a router or agateway. For instance, at least one of apparatus 210 and apparatus 220may be implemented in an eNodeB in an LTE, LTE-Advanced or LTE-AdvancedPro network or in a gNB in a 5G, NR, IoT or NB-IoT network.Alternatively, at least one of apparatus 210 and apparatus 220 may beimplemented in the form of one or more IC chips such as, for example andwithout limitation, one or more single-core processors, one or moremulti-core processors, or one or more CISC or RISC processors.

In one aspect, each of processor 212 and processor 222 may beimplemented in the form of one or more single-core processors, one ormore multi-core processors, or one or more CISC or RISC processors. Thatis, even though a singular term “a processor” is used herein to refer toprocessor 212 and processor 222, each of processor 212 and processor 222may include multiple processors in some implementations and a singleprocessor in other implementations in accordance with the presentdisclosure. In another aspect, each of processor 212 and processor 222may be implemented in the form of hardware (and, optionally, firmware)with electronic components including, for example and withoutlimitation, one or more transistors, one or more diodes, one or morecapacitors, one or more resistors, one or more inductors, one or morememristors and/or one or more varactors that are configured and arrangedto achieve specific purposes in accordance with the present disclosure.In other words, in at least some implementations, each of processor 212and processor 222 is a special-purpose machine specifically designed,arranged and configured to perform specific tasks including handling ofinvalid mandatory information in mobile communications in accordancewith various implementations of the present disclosure.

In some implementations, apparatus 210 may also include a transceiver216, as a communication device, coupled to processor 212 and capable ofwirelessly transmitting and receiving data. In some implementations,apparatus 210 may further include a memory 214 coupled to processor 212and capable of being accessed by processor 212 and storing data therein.In some implementations, apparatus 220 may also include a transceiver226, as a communication device, coupled to processor 222 and capable ofwirelessly transmitting and receiving data. In some implementations,apparatus 220 may further include a memory 224 coupled to processor 222and capable of being accessed by processor 222 and storing data therein.Accordingly, apparatus 210 and apparatus 220 may wirelessly communicatewith each other via transceiver 216 and transceiver 226, respectively.

To aid better understanding, the following description of theoperations, functionalities and capabilities of each of apparatus 210and apparatus 220 is provided in the context of an NR communicationenvironment in which apparatus 210 is implemented in or as a UE (e.g.,UE 110) and apparatus 220 is implemented in or as a network node (e.g.,network node 125) of a wireless network (e.g., wireless network 120).

In one aspect of handling of invalid mandatory information in mobilecommunications in accordance with the present disclosure, processor 212of apparatus 210 may receive, via transceiver 216, a 5GSM message fromapparatus 220 as a network node of a wireless network. Additionally,processor 212 may determine that there is an error encountered with amandatory IE in the 5GSM message. Moreover, processor 212 may handle theerror in a way specific to a PDU session procedure corresponding to the5GSM message.

In some implementations, the 5GSM message may include a PDU SESSIONESTABLISHMENT ACCEPT message. In such cases, in handling the error,processor 212 may initiate a PDU session release procedure. In someimplementations, in initiating the PDU session release procedure,processor 212 may send, via transceiver 216, a PDU SESSION RELEASEREQUEST message to apparatus 220 with a 5GSM cause #96 to indicateinvalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSIONMODIFICATION COMMAND message. In such cases, in handling the error,processor 212 may send, via transceiver 216, a PDU SESSION MODIFICATIONCOMMAND REJECT message to apparatus 220 with a 5GSM cause #96 toindicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSIONRELEASE COMMAND message. In such cases, in handling the error, processor212 may send, via transceiver 216, a PDU SESSION RELEASE COMPLETEmessage to apparatus 220 with a 5GSM cause #96 to indicate invalidmandatory information.

In another aspect of handling of invalid mandatory information in mobilecommunications in accordance with the present disclosure, processor 212of apparatus 210 may determine that there is an error encountered with amandatory IE in a 5GSM message from apparatus 220 as a network node of awireless network. Furthermore, processor 212 may handle the error in away depending on to which PDU session procedure the 5GSM messagecorresponds. In some implementations, the PDU session procedure to whichthe 5GSM message corresponds may include a PDU session establishmentprocedure, a PDU session modification procedure, or a PDU sessionrelease procedure.

In some implementations, the 5GSM message may include a PDU SESSIONESTABLISHMENT ACCEPT message. In such cases, in handling the error,processor 212 may initiate a PDU session release procedure. In someimplementations, in initiating the PDU session release procedure,processor 212 may send, via transceiver 216, a PDU SESSION RELEASEREQUEST message to apparatus 220 with a 5GSM cause #96 to indicateinvalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSIONMODIFICATION COMMAND message. In such cases, in handling the error,processor 212 may send, via transceiver 216, a PDU SESSION MODIFICATIONCOMMAND REJECT message to apparatus 220 with a 5GSM cause #96 toindicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSIONRELEASE COMMAND message. In such cases, in handling the error, processor212 may send, via transceiver 216, a PDU SESSION RELEASE COMPLETEmessage to apparatus 220 with a 5GSM cause #96 to indicate invalidmandatory information.

Illustrative Processes

FIG. 3 illustrates an example process 300 in accordance with animplementation of the present disclosure. Process 300 may be an exampleimplementation of the proposed schemes described above with respect tohandling of invalid mandatory information in mobile communications inaccordance with the present disclosure. Process 300 may represent anaspect of implementation of features of apparatus 210 and apparatus 220.Process 300 may include one or more operations, actions, or functions asillustrated by one or more of blocks 310, 320 and 330. Althoughillustrated as discrete blocks, various blocks of process 300 may bedivided into additional blocks, combined into fewer blocks, oreliminated, depending on the desired implementation. Moreover, theblocks of process 300 may executed in the order shown in FIG. 3 or,alternatively, in a different order. Process 300 may also be repeatedpartially or entirely. Process 300 may be implemented by apparatus 210,apparatus 220 and/or any suitable wireless communication device, UE,base station or machine type devices. Solely for illustrative purposesand without limitation, process 300 is described below in the context ofapparatus 210 in or as a UE and apparatus 220 in or as a network node ofa wireless network (e.g., 5G NR mobile network). Process 300 may beginat block 310.

At 310, process 300 may involve processor 212 of apparatus 210receiving, via transceiver 216, a 5GSM message from apparatus 220 as anetwork node of a wireless network. Process 300 may proceed from 310 to320.

At 320, process 300 may involve processor 212 determining that there isan error encountered with a mandatory information element (IE) in the5GSM message. Process 300 may proceed from 320 to 330.

At 330, process 300 may involve processor 212 handling the error in away specific to a PDU session procedure corresponding to the 5GSMmessage.

In some implementations, the 5GSM message may include a PDU SESSIONESTABLISHMENT ACCEPT message. In such cases, in handling the error,process 300 may involve processor 212 initiating a PDU session releaseprocedure. In some implementations, in initiating the PDU sessionrelease procedure, process 300 may involve processor 212 sending, viatransceiver 216, a PDU SESSION RELEASE REQUEST message to apparatus 220with a 5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSIONMODIFICATION COMMAND message. In such cases, in handling the error,process 300 may involve processor 212 sending, via transceiver 216, aPDU SESSION MODIFICATION COMMAND REJECT message to apparatus 220 with a5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSIONRELEASE COMMAND message. In such cases, in handling the error, process300 may involve processor 212 sending, via transceiver 216, a PDUSESSION RELEASE COMPLETE message to apparatus 220 with a 5GSM cause #96to indicate invalid mandatory information.

FIG. 4 illustrates an example process 400 in accordance with animplementation of the present disclosure. Process 400 may be an exampleimplementation of the proposed schemes described above with respect tohandling of invalid mandatory information in mobile communications inaccordance with the present disclosure. Process 400 may represent anaspect of implementation of features of apparatus 210 and apparatus 220.Process 400 may include one or more operations, actions, or functions asillustrated by one or more of blocks 410 and 420. Although illustratedas discrete blocks, various blocks of process 400 may be divided intoadditional blocks, combined into fewer blocks, or eliminated, dependingon the desired implementation. Moreover, the blocks of process 400 mayexecuted in the order shown in FIG. 4 or, alternatively, in a differentorder. Process 400 may also be repeated partially or entirely. Process400 may be implemented by apparatus 210, apparatus 220 and/or anysuitable wireless communication device, UE, base station or machine typedevices. Solely for illustrative purposes and without limitation,process 400 is described below in the context of apparatus 210 in or asa UE and apparatus 220 in or as a network node of a wireless network(e.g., 5G NR mobile network). Process 400 may begin at block 410.

At 410, process 400 may involve processor 212 of apparatus 210determining that there is an error encountered with a mandatory IE in a5GSM message from apparatus 220 as a network node of a wireless network.Process 400 may proceed from 410 to 420.

At 420, process 400 may involve processor 212 handling the error in away depending on to which PDU session procedure the 5GSM messagecorresponds.

In some implementations, the PDU session procedure to which the 5GSMmessage corresponds may include a PDU session establishment procedure, aPDU session modification procedure, or a PDU session release procedure.

In some implementations, the 5GSM message may include a PDU SESSIONESTABLISHMENT ACCEPT message. In such cases, in handling the error,process 400 may involve processor 212 initiating a PDU session releaseprocedure. In some implementations, in initiating the PDU sessionrelease procedure, process 400 may involve processor 212 sending, viatransceiver 216, a PDU SESSION RELEASE REQUEST message to apparatus 220with a 5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSIONMODIFICATION COMMAND message. In such cases, in handling the error,process 400 may involve processor 212 sending, via transceiver 216, aPDU SESSION MODIFICATION COMMAND REJECT message to apparatus 220 with a5GSM cause #96 to indicate invalid mandatory information.

In some implementations, the 5GSM message may include a PDU SESSIONRELEASE COMMAND message. In such cases, in handling the error, process400 may involve processor 212 sending, via transceiver 216, a PDUSESSION RELEASE COMPLETE message to apparatus 220 with a 5GSM cause #96to indicate invalid mandatory information.

ADDITIONAL NOTES

The herein-described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely examples, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

Further, with respect to the use of substantially any plural and/orsingular terms herein, those having skill in the art can translate fromthe plural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

Moreover, it will be understood by those skilled in the art that, ingeneral, terms used herein, and especially in the appended claims, e.g.,bodies of the appended claims, are generally intended as “open” terms,e.g., the term “including” should be interpreted as “including but notlimited to,” the term “having” should be interpreted as “having atleast,” the term “includes” should be interpreted as “includes but isnot limited to,” etc. It will be further understood by those within theart that if a specific number of an introduced claim recitation isintended, such an intent will be explicitly recited in the claim, and inthe absence of such recitation no such intent is present. For example,as an aid to understanding, the following appended claims may containusage of the introductory phrases “at least one” and “one or more” tointroduce claim recitations. However, the use of such phrases should notbe construed to imply that the introduction of a claim recitation by theindefinite articles “a” or “an” limits any particular claim containingsuch introduced claim recitation to implementations containing only onesuch recitation, even when the same claim includes the introductoryphrases “one or more” or “at least one” and indefinite articles such as“a” or “an,” e.g., “a” and/or “an” should be interpreted to mean “atleast one” or “one or more;” the same holds true for the use of definitearticles used to introduce claim recitations. In addition, even if aspecific number of an introduced claim recitation is explicitly recited,those skilled in the art will recognize that such recitation should beinterpreted to mean at least the recited number, e.g., the barerecitation of “two recitations,” without other modifiers, means at leasttwo recitations, or two or more recitations. Furthermore, in thoseinstances where a convention analogous to “at least one of A, B, and C,etc.” is used, in general such a construction is intended in the senseone having skill in the art would understand the convention, e.g., “asystem having at least one of A, B, and C” would include but not belimited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc. In those instances where a convention analogous to “atleast one of A, B, or C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention, e.g., “a system having at least one of A, B, or C” wouldinclude but not be limited to systems that have A alone, B alone, Calone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc. It will be further understood by those withinthe art that virtually any disjunctive word and/or phrase presenting twoor more alternative terms, whether in the description, claims, ordrawings, should be understood to contemplate the possibilities ofincluding one of the terms, either of the terms, or both terms. Forexample, the phrase “A or B” will be understood to include thepossibilities of “A” or “B” or “A and B.”

From the foregoing, it will be appreciated that various implementationsof the present disclosure have been described herein for purposes ofillustration, and that various modifications may be made withoutdeparting from the scope and spirit of the present disclosure.Accordingly, the various implementations disclosed herein are notintended to be limiting, with the true scope and spirit being indicatedby the following claims.

What is claimed is:
 1. A method, comprising: receiving, by a processorof an apparatus, a 5th Generation session management (5GSM) message froma network node of a wireless network; determining, by the processor,that there is an error encountered with a mandatory information element(IE) in the 5GSM message; and handling, by the processor, the error in away specific to a protocol data unit (PDU) session procedurecorresponding to the 5GSM message.
 2. The method of claim 1, wherein the5GSM message comprises a PDU SESSION ESTABLISHMENT ACCEPT message, andwherein the handling of the error comprises initiating a PDU sessionrelease procedure.
 3. The method of claim 2, wherein the initiating ofthe PDU session release procedure comprises sending a PDU SESSIONRELEASE REQUEST message to the network node with a 5GSM cause #96 toindicate invalid mandatory information.
 4. The method of claim 1,wherein the 5GSM message comprises a PDU SESSION MODIFICATION COMMANDmessage, and wherein the handling of the error comprises sending a PDUSESSION MODIFICATION COMMAND REJECT message to the network node with a5GSM cause #96 to indicate invalid mandatory information.
 5. The methodof claim 1, wherein the 5GSM message comprises a PDU SESSION RELEASECOMMAND message, and wherein the handling of the error comprises sendinga PDU SESSION RELEASE COMPLETE message to the network node with a 5GSMcause #96 to indicate invalid mandatory information.
 6. A method,comprising: determining, by a processor of an apparatus, that there isan error encountered with a mandatory information element (IE) in a 5thGeneration session management (5GSM) message from a network node of awireless network; and handling, by the processor, the error in a waydepending on to which protocol data unit (PDU) session procedure the5GSM message corresponds, wherein the PDU session procedure to which the5GSM message corresponds comprises a PDU session establishmentprocedure, a PDU session modification procedure, or a PDU sessionrelease procedure.
 7. The method of claim 6, wherein the 5GSM messagecomprises a PDU SESSION ESTABLISHMENT ACCEPT message, and wherein thehandling of the error comprises initiating a PDU session releaseprocedure.
 8. The method of claim 7, wherein the initiating of the PDUsession release procedure comprises sending a PDU SESSION RELEASEREQUEST message to the network node with a 5GSM cause #96 to indicateinvalid mandatory information.
 9. The method of claim 6, wherein the5GSM message comprises a PDU SESSION MODIFICATION COMMAND message, andwherein the handling of the error comprises sending a PDU SESSIONMODIFICATION COMMAND REJECT message to the network node with a 5GSMcause #96 to indicate invalid mandatory information.
 10. The method ofclaim 6, wherein the 5GSM message comprises a PDU SESSION RELEASECOMMAND message, and wherein the handling of the error comprises sendinga PDU SESSION RELEASE COMPLETE message to the network node with a 5GSMcause #96 to indicate invalid mandatory information.
 11. An apparatus,comprising: a transceiver configured to wirelessly communicate with anetwork node of a wireless network; and a processor coupled to thetransceiver and configured to perform operations comprising: receiving,via the transceiver, a 5th Generation session management (5GSM) messagefrom the network node; determining that there is an error encounteredwith a mandatory information element (IE) in the 5GSM message; andhandling the error in a way specific to a protocol data unit (PDU)session procedure corresponding to the 5GSM message.
 12. The apparatusof claim 11, wherein the 5GSM message comprises a PDU SESSIONESTABLISHMENT ACCEPT message, and wherein, in handling the error, theprocessor is configured to initiate a PDU session release procedure. 13.The apparatus of claim 12, wherein, in initiating the PDU sessionrelease procedure, the processor is configured to send, via thetransceiver, a PDU SESSION RELEASE REQUEST message to the network nodewith a 5GSM cause #96 to indicate invalid mandatory information.
 14. Theapparatus of claim 11, wherein the 5GSM message comprises a PDU SESSIONMODIFICATION COMMAND message, and wherein, in handling the error, theprocessor is configured to send, via the transceiver, a PDU SESSIONMODIFICATION COMMAND REJECT message to the network node with a 5GSMcause #96 to indicate invalid mandatory information.
 15. The apparatusof claim 11, wherein the 5GSM message comprises a PDU SESSION RELEASECOMMAND message, and wherein, in handling the error, the processor isconfigured to send, via the transceiver, a PDU SESSION RELEASE COMPLETEmessage to the network node with a 5GSM cause #96 to indicate invalidmandatory information.